Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

Compiling Progress 4GL procedures

The COMPILE statement lets you compile the Progress 4GL procedures and save the compilations to disk. This speeds up your application since the Progress 4GL does not have to recompile it every time you want to run a procedure.

To compile procedures that access an ORACLE database, start up the OpenEdge procedure editor and connect to the schema holder for your target ORACLE database using the schema holder’s logical database name. Then use the COMPILE statement. If you change the name of the schema holder after compiling a procedure, you must connect to the renamed schema holder and recompile the procedure. You do not have to connect to the target ORACLE database to compile a procedure. For more information, see the “COMPILE Statement” reference entry in OpenEdge Development: Progress 4GL Reference .

R-code

The r-code is not portable among database management systems. For example, code that you have compiled for an ORACLE database will not run with an OpenEdge database.

The size of r-code can grow when you compile procedures against an ORACLE database as compared with compiling against an OpenEdge database. The r-code for a DataServer application contains as text the portions of SQL statements that the DataServer passes to ORACLE.